Skip to content

Conversation

@k0d13
Copy link
Owner

@k0d13 k0d13 commented Jan 15, 2026

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Patch Changes

  • 50210ec: Bump patch supported range to 16.1.3
  • e893fb2: Bump patch supported range to 16.1.2

Summary by CodeRabbit

Release Notes

  • Patch Release
    • Version 2.1.14 released
    • Updated patch-supported range to 16.1.3 and 16.1.2

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link

coderabbitai bot commented Jan 15, 2026

Walkthrough

A patch release (v2.1.14) of the next-ws package with updated Next.js supported patch range to 16.1.2. The release entry is formally documented in the changelog, and the changeset file is removed as part of the release process.

Changes

Cohort / File(s) Summary
Release metadata
package.json, CHANGELOG.md, .changeset/V6CUYgqg3Xi42.md
Version bumped from 2.1.13 to 2.1.14; new changelog entry added documenting the patch range update to 16.1.2; changeset entry removed post-release

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested labels

patches

Poem

🐰 A patch hops in, version now 2.1.14,
Next.js sixteen-point-one-point-two's here to stay,
Changelog updated, changeset put away,
Release notes tidied, all neat and tidy today! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title "Pending Releases" is generic and vague, failing to convey meaningful information about the specific package version bump or changeset being released. Consider using a more descriptive title such as "Release [email protected]" or "Bump next-ws patch version to 2.1.14" to clearly communicate the main change.
✅ Passed checks (2 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions bot force-pushed the changeset-release/main branch from 0739dbf to 4060167 Compare January 17, 2026 00:22
@k0d13 k0d13 merged commit fe37c19 into main Jan 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants